Lotus Notes client crashing with embedded MS Web browser control showing Flash file

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: Lotus Notes client crashing with embedded MS Web browser control showing Flash file

Feedback Type: Problem

Product Area: Notes Client

Technical Area: Crash

Platform: Windows

Release: 8.5.3

Reproducible: Always

We have started seeing many of our Lotus Notes clients crashing throughout the organization, and have isolated the problem to a dynamic Flash (graphs) file embedded into a Notes form via a MS Web Browser control.

To ensure this was truly the culprit, I built an extremely basic Notes database with a single form, single field, and the embedded browser control pointing to a simple .SWF file.

Sure enough, as soon as the mouse hovers over the embedded control, the client crashes. This is 100% reproducible.

We have tested this with clients ranging from 7.0.2, right up to 8.5.3FP4, and the result is always the same. We are now in the process of trying to determine if it is an IE version issue or an Adobe Flash version issue, but it has completely wrecked the effectiveness of our application.

A review of the resulting NSD files shows a pretty common fatal thread report...

############################################################
### FATAL THREAD 1/31 [ NLNOTES: 0e50: 2118]
### FP=0x00189204, PC=0x5af4cd7b, SP=0x001891c8
### stkbase=00190000, total stksize=241664, used stksize=28216
### EAX=0x00000000, EBX=0x002e05f2, ECX=0x00000000, EDX=0x00000000
### ESI=0x0bee0418, EDI=0x00000000, CS=0x00000023, SS=0x0000002b
### DS=0x0000002b, ES=0x0000002b, FS=0x00000053, GS=0x0000002b Flags=0x00010246
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
[ 1] 0x5af4cd7b mshtml.TravelLogCreateInstance+1383284 (189420,2e05f2,189310,1892c0)
[ 2] 0x5af4cd30 mshtml.TravelLogCreateInstance+1383209 (189420,2e05f2,0,189310)
[ 3] 0x5b649144 mshtml.RunHTMLApplication+2062348 (2e05f2,200,0,9100c5)
[ 4] 0x76a562fa USER32.gapfnScSendMessage+818 (5b648ce4,2e05f2,200,0)
[ 5] 0x76a56d3a USER32.GetThreadDesktop+215 (0,5b648ce4,2e05f2,200)
[ 6] 0x76a577c4 USER32.CharPrevW+312 (5b648ce4,0,18977c,630b914b)
[ 7] 0x76a5788a USER32.DispatchMessageW+15 (189758,1,b08b4,63020000)
@[ 8] 0x630b914b nnotesws.NEMMainLoop@4+811 (4013a0)
@[ 9] 0x00401a41 NLNOTES.WinMain@16+1697 (630f6920,0,273da5,0)
@[10] 0x00402721 NLNOTES.WinMainCRTStartup+389 (fffde000,18ffd4,76f99ef2,fffde000)
[11] 0x74a433aa kernel32.BaseThreadInitThunk+18 (fffde000,777edf6c,0,0)
[12] 0x76f99ef2 ntdll.RtlInitializeExceptionChain+99 (40259c,fffde000,0,0)
[13] 0x76f99ec5 ntdll.RtlInitializeExceptionChain+54 (40259c,fffde000,0,78746341)

I have tried searching for some sort of clue to the origin of the crashes, but I'm coming up short.

Has anyone else observed this behaviour, and if so, have you had any luck preventing the crash?

Any/all advice would be most appreciated!

Feedback number WEBB98424P created by ~Wei Asatoopulakol on 05/27/2013

Status: Open
Comments: